home *** CD-ROM | disk | FTP | other *** search
- Path: dawn.mmm.com!news
- From: kjhopps@mmm.com (Kevin J Hopps)
- Newsgroups: comp.lang.c++
- Subject: Re: Aborting Constructors, Part II
- Date: 6 Feb 1996 13:45:02 GMT
- Organization: 3M - St. Paul, MN 55144-1000 US
- Message-ID: <4f7m0u$4g4@dawn.mmm.com>
- References: <4eoeck$t6n@news.ios.com> <4eq99t$fpu@fsuj01.rz.uni-jena.de> <marnoldDM529E.3CH@netcom.com> <mikec.823353055@atl1>
- Reply-To: kjhopps@mmm.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael J. Callahan (mikec@atl1.america.net) wrote:
-
- [ snip ]
-
- > So under the covers, a new allocates raw memory for the object to occupy,
- > and begins running the ctor on that raw memory. Within the ctor, if an
- > exception is thrown, the raw memory allocation if deallocated, the instance
- > in effect no longer exists?
-
- > Is that recent behavior to the evolving std, or did I just miss it? If
- > recent, is it implemented in many compilers yet?
-
- I believe it has been there more than a year. I don't know about many
- compilers, but SunSoft C++ operates correctly.
- --
- Kevin J. Hopps e-mail: kjhopps@mmm.com
- 3M Company phone: (612) 737-4643
- 3M Center, Bldg. 235-2D-57 fax: (612) 737-2700
- St. Paul, MN 55144-1000 Opinions are my own. I don't speak for 3M.
- But 3M speaks for me -- I did not write the following line:
-
- Opinions expressed herein are my own and may not represent those of 3M.
-